Repository navigation
Release by publishing the release-drafter draft - #47
Merged
Merged
Conversation
A release meant pushing a tag by hand and choosing its version, and the release notes were generated from whatever had merged, labelled or not. Now release-drafter keeps a draft current from the labels of merged pull requests, pr-labels makes every pull request carry exactly one, and publishing the draft is the release: it creates the tag and fires `release: published` on ci.yml. A pushed tag alone no longer releases. The NuGet and npm release jobs stay in ci.yml, in the `release` environment, because the trusted publishing policies on nuget.org and npm name that file and that environment. The GitHub release is the published draft, so the job no longer creates one; it attaches the packages with `gh release upload --clobber`, which a re-run can repeat safely. Dependabot updates NuGet, npm (js/journeys) and actions weekly. The releasing, breaking-changes and upgrade-deps skills describe the flow, and `mise run release` shows the draft. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cdp now releases when its release-drafter draft is published (on github.com, from a phone, or with
mise run release publish), not when a tag is pushed. Each pull request carries exactly one label, and that label decides the next version.Prompt summary: Bring every nullean repository onto one standard: .NET 11, global.json, mise for bootstrapping SDKs, the same mise run task names, and zizmor on every repository's workflows. This step makes every repository release the same way: release-drafter drafts the notes from required PR labels, in 0.x a breaking change bumps the minor version, and releasing means promoting the draft.
Why
A release meant pushing a tag by hand and choosing its version, and
gh release create --generate-noteswrote the notes from whatever had merged since the last tag. Nothing required a PR label, so the notes and the next version depended on the person tagging.What
Release from the draft
ci.ymlreplaces its tag trigger withrelease: published. Therelease(NuGet) andpublish-npmjobs now run whengithub.event_name == 'release', after the same jobs as before. They stay inci.ymland in thereleaseenvironment, because the trusted publishing policies on nuget.org and npm name that file and that environment, and that environment only lets tags deploy (a published release's ref is its tag). The release now exists before the job runs (it is the published draft), so the job no longer creates one. It attaches the packages withgh release upload --clobber, which a re-run can repeat. The cdp release jobs stay bespoke rather than calling the sharedrelease.yml, because they publish native AOT tool packages per RID plus npm.Drafts, labels and dependency updates
release-drafter.ymlkeeps the draft current on every push to main..github/release-drafter.ymlmaps labels to versions:breaking,featureandenhancementbump the minor version (the 0.x rule), and everything else is a patch.pr-labels.ymlfails a PR without exactly one release label. Both call the shared workflows pinned at v1.3.0. The label set was synced in #45.dependabot.ymlupdates NuGet, npm (js/journeys) and actions weekly in groups, with a 7-day cooldown and thedependencieslabel.Skills and docs
The
releasing,breaking-changesandupgrade-depsskills come from the template, with one line inreleasingabout the npm job. Theprskill comes too, with thecommitskill andwriting-style.mdit links to.mise run releaseshows the draft andmise run release publishpublishes it. AGENTS.md has a releasing section, and the DECISIONS.md release entry now describes the new flow.Out of scope: making
release-labela required check in branch protection, curb formatting (the template'sformatskill is left out until that step), and the template'sissueskill.Verify
mise run ciwith Chrome andCDP_BROWSER_REQUIRED=1: 517/517 .NET tests passed (0 skipped), npm 419 passed, Playwright 4 passed. These are the same counts as on main.zizmor --min-severity medium .reports no findings;actionlintis clean.mise run releasereports no draft yet, as expected until a labelled PR merges after this one.🤖 Generated with Claude Code